-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rm: linux-disk-encryption: document re-encryption #621
Conversation
Docs for 182b37f are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2451/docs/artifacts/html/index.html |
Docs for fb9b0c6 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2452/docs/artifacts/html/index.html |
Docs for b21768f are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2453/docs/artifacts/html/index.html |
Docs for aa0289b are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2454/docs/artifacts/html/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As always, it's a pleasure to read your texts! I only made a few double-checking and tiny suggestions, but the text is excellent!
Docs for 9feb2c3 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2458/docs/artifacts/html/index.html |
Docs for c84e5d0 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2460/docs/artifacts/html/index.html |
Docs for 4430eaf are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2464/docs/artifacts/html/index.html |
sorry Diane, this gave me extra motivation to try and do a better job and I reorganized things a bit more. Maybe you can have a look? it is your fault for the encouragement :) |
Document LUKS2 re-encryption and PKCS#11 emulation. Signed-off-by: Jorge Ramirez-Ortiz <[email protected]> Reviewed-by: Daiane Angolini <[email protected]>
Docs for d375aed are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2465/docs/artifacts/html/index.html |
I will review again and "resolve" everything I think is resolved from my pov ;) I'm glad you got motivated <3 |
Great changes! it's a looks great to me ;) |
|
||
.. note:: | ||
|
||
If the system is restarted before the non-blocking re-encryption |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ldts Are we 100% sure this is true? We have clients that are using re-encryption and it picks up where it left off and does not block the boot in their case. Did something change here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes 100%.
I am not sure what configuration they might be running but in our case as soon as we enroll the TPM/PKCS11 tokens, we remove the passphrase and initiate the re-encryption.
If the volume is closed without having completed re-encryption, it just cant be opened again. It is easy to prototype locally on any machine (create a file of ~60MB, create an ext4 filesystem, and encrypt it with luks).
but tell me more about the configuration of those clients so I can see how they differ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
um, are you sure about what your clients are reporting??
with the current code in the baseline, if online reencryption didnt finish and the board reboots we are going to block initramfs until it completes (resume is a blocking call)
having said that, this segment of code seems to succeed at opening ? which is kind of weird...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some suggestions, but it LGTM!
Co-authored-by: Katrina Prosise <[email protected]>
Co-authored-by: Katrina Prosise <[email protected]>
Co-authored-by: Katrina Prosise <[email protected]>
Co-authored-by: Katrina Prosise <[email protected]>
Co-authored-by: Katrina Prosise <[email protected]>
Docs for efb04d2 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2467/docs/artifacts/html/index.html |
Docs for 79977a1 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2468/docs/artifacts/html/index.html |
Docs for 38c5b50 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2469/docs/artifacts/html/index.html |
Docs for 3a71ee8 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2470/docs/artifacts/html/index.html |
Docs for 285b686 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2471/docs/artifacts/html/index.html |
@ldts whenever you are ready for this to be merged, squash the commits and give me the word! |
Docs for aa10607 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2520/docs/artifacts/html/index.html |
Document LUKS2 re-encryption and PKCS#11 emulation.
Readiness
Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."
make linkcheck
.-s, --signoff
).-S, --gpg-sign
).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.